Deprecate md5() and weak algos in passwordless API & normal login - #460
Conversation
Doc update reflecting future patch People willing to continue using md5 or any other algo will be able to do so with an explicit filter, so no breaking change.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
website | f6200be | Commit Preview URL Branch Preview URL |
Aug 25 2026, 09:31 AM |
Co-authored-by: dgw <dgw@technobabbl.es>
ozh
changed the title
Updated the example signature token to a 32 character string and clarified customization options.
|
(I undrafted this PR a couple days ago but then I'm still adding stuff, a bit dumb from me :) the real green sign for merging will be when I finish 4111. In the meantime, feel free to revise or reword anything here of course) |
|
To be merged when 1.10.5 goes live 🚀 |
|
So. I cannot merge the PR with the blog post for 1.10.5 because no one has formally approved. I cannot merge here because somehow resolving a merge conflict has invalidated @LeoColomb's review. I cannot find the settings that would allow me to merge without waiting for a review. This whole bureaucracy process is seriously pissing me off. This isn't collaboration : this is bureaucracy. Someone please review and merge here + release 1.10.5 on YOURLS/YOURLS |
3 participants
Doc update reflecting future patch
People willing to continue using md5 or any other algo will be able to do so with an explicit filter, so no breaking change.
Ref: YOURLS/YOURLS#4111